System, method and computer program product for geo specific vehicle pricing

ABSTRACT

Disclosed are embodiments for the aggregation and analysis of vehicle prices via a geo-specific model. Data may be collected at various geo-specific levels such as a ZIP-Code level to provide greater data resolution. Data sets taken into account may include demarcation point data sets and data sets based on vehicle transactions. A demarcation point data set may be based on consumer market factors that influence car-buying behavior. Vehicle transactions may be classified into data sets for other vehicles having similar characteristics to the vehicle. A geo-specific statistical pricing model may then be applied to the data sets based on similar characteristics to a particular vehicle to produce a price estimation for the vehicle.

CROSS-REFERENCE TO RELATED APPLICATION

This application is a continuation of, and claims a benefit of priority under 35 U.S.C. 120 of the filing date of U.S. patent application Ser. No. 15/391,563 filed Dec. 27, 2016, entitled “System, Method and Computer Program Product for Geo-Specific Vehicle Pricing”, which is a continuation of and claims a benefit of priority under 35 U.S.C. 120 of the filing date of U.S. patent application Ser. No. 13/173,357 filed Jun. 30, 2011, issued as U.S. Pat. No. 10,296,929, entitled “System, Method and Computer Program Product for Geo-Specific Vehicle Pricing”, the entire contents of which are hereby expressly incorporated by reference for all purposes.

TECHNICAL FIELD

This disclosure relates generally to pricing vehicles in a marketplace. More particularly, embodiments disclosed herein relate to a system, method, and computer program product for geo-specific vehicle pricing.

BACKGROUND OF THE RELATED ART

When purchasing a vehicle, consumers are often faced with the problem in finding and/or understanding what the true value for a vehicle might be. Today's vehicle marketplace offers a multitude of methods for pricing vehicles. Unfortunately, these methods often report inconsistent or even conflicting prices for vehicles. Furthermore, conventional methods for vehicle pricing are generally based on administrative boundaries, such as countries, U.S. Census regions, and states. Consumers searching for a vehicle in geographic areas smaller than U.S. Census regions may face additional challenges as pricing data in such areas tend to be sparse, resulting in vehicle prices for the same model and trim vary greatly from area to area.

Complicating the matter is the fact that consumers often do not have sufficient, relevant, and/or accurate information on a particular vehicle or does not understand such information, including interdependence between local demand and availability of the vehicle. To illustrate with a specific example, a recommended price (e.g., $20,000) for a particular vehicle model and trim may not take into account how sensitive that price is (“Is $19,000 a good or bad price for this vehicle model and trim in a beach town on an island?”) or how the vehicle model compares to another vehicle model with a similar trim at about the same price. Consequently, there is always room for improvement.

SUMMARY OF THE DISCLOSURE

Embodiments disclosed herein provide a system, method, and computer program product for a geo-specific model for estimation of vehicle prices. In some embodiments, geographic regions may be classified into regions smaller than U.S. Census regions. For example, geographic regions may include ZIP-Code tabulation areas, sub-Designated Market Areas, Designated Market Areas, Designated Market Groups and Designated Market Regions. In some embodiments, vehicle transactions are also taken into account. The transaction data may be aggregated from various data sets. In some embodiments, geographic regions and vehicle transaction data may be then be applied to a statistical model to obtain a vehicle price.

In some embodiments, a method for pricing a vehicle in a geographic region may comprise, by a computing device, applying a regression model to a first set of variables, a second set of variables, and a third set of variables. The first set of variables may represent vehicle-specific attributes, the second set of variables may represent industry data and vehicle supply and demand, and the third set of variables may represent local-level customer and demographic factors that influence car-buying behavior in the geographic region. Examples of the third set of variables may include geo-specific socioeconomic variables. A predicted margin ratio may be generated for the vehicle based on results from the regression model and applied to a cost of the vehicle to generate a geo-specific price estimation for the vehicle in the geographic region. In some embodiments, the results from the regression model may be adjusted based on a number of observations, which may be generated utilizing temporally-weighted historical data, to account for geographic biases. The geographic region may represent or be smaller than a designated market area, or it may represent a ZIP Code or some other geographical boundary.

Software implementing embodiments disclosed herein may be implemented in suitable computer-executable instructions that may reside on one or more non-transitory computer-readable storage media. Within this disclosure, the term “computer-readable medium” encompasses all types of data storage medium that can be read by at least one processor. Examples of a computer-readable medium can include random access memories, read-only memories, hard drives, data cartridges, magnetic tapes, floppy diskettes, flash memory drives, optical data storage devices, compact-disc read-only memories, and other appropriate computer memories and data storage devices.

Embodiments disclosed herein can provide many advantages. For example, in some embodiments, the geo-specific model may provide for a vehicle estimation that is both geographic and data driven. In some embodiments, vehicle transaction data may be collected at the ZIP-Code level. This may provide for fine data resolution in addition to transaction data at a larger region. This may present a clear picture of vehicle pricing based on geographic regions.

These, and other, aspects of the disclosure will be better appreciated and understood when considered in conjunction with the following description and the accompanying drawings. It should be understood, however, that the following description, while indicating various embodiments of the disclosure and numerous specific details thereof, is given by way of illustration and not of limitation. Many substitutions, modifications, additions and/or rearrangements may be made within the scope of the disclosure without departing from the spirit thereof, and the disclosure includes all such substitutions, modifications, additions and/or rearrangements.

BRIEF DESCRIPTION OF THE DRAWINGS

The drawings accompanying and forming part of this specification are included to depict certain aspects of the disclosure. It should be noted that the features illustrated in the drawings are not necessarily drawn to scale. A more complete understanding of the disclosure and the advantages thereof may be acquired by referring to the following description, taken in conjunction with the accompanying drawings in which like reference numbers indicate like features and wherein:

FIG. 1 depicts one embodiment of a topology including a vehicle data system;

FIG. 2 depicts one embodiment of a model that transforms data into vehicle prices;

FIG. 3 depicts one embodiment of a model that uses data used to obtain vehicle price;

FIG. 4 depicts a flow diagram illustrating one example embodiment of a method for determining merging between geographical units;

FIG. 5 depicts one embodiment of adjacent geographical units;

FIG. 6 depicts a one embodiment of example geographical units for Los Angeles, California;

FIG. 7 depicts one embodiment of a consumer-based hierarchy;

FIG. 8 depicts a flow diagram illustrating one example embodiment of a method for determining a geo-specific price estimate; and

FIG. 9 depicts a diagram illustrating one embodiment of temporal weight functions for degradation factors.

DETAILED DESCRIPTION

The disclosure and various features and advantageous details thereof are explained more fully with reference to the exemplary, and therefore non-limiting, embodiments illustrated in the accompanying drawings and detailed in the following description. Descriptions of known programming techniques, computer software, hardware, operating platforms and protocols may be omitted so as not to unnecessarily obscure the disclosure in detail. It should be understood, however, that the detailed description and the specific examples, while indicating the preferred embodiments, are given by way of illustration only and not by way of limitation. Various substitutions, modifications, additions and/or rearrangements within the spirit and/or scope of the underlying inventive concept will become apparent to those skilled in the art from this disclosure.

As used herein, the terms “comprises,” “comprising,” “includes,” “including,” “has,” “having,” or any other variation thereof, are intended to cover a non-exclusive inclusion. For example, a process, product, article, or apparatus that comprises a list of elements is not necessarily limited only those elements but may include other elements not expressly listed or inherent to such process, product, article, or apparatus. Further, unless expressly stated to the contrary, “or” refers to an inclusive or and not to an exclusive or. For example, a condition A or B is satisfied by any one of the following: A is true (or present) and B is false (or not present), A is false (or not present) and B is true (or present), and both A and B are true (or present).

Additionally, any examples or illustrations given herein are not to be regarded in any way as restrictions on, limits to, or express definitions of, any term or terms with which they are utilized. Instead these examples or illustrations are to be regarded as being described with respect to one particular embodiment and as illustrative only. Those of ordinary skill in the art will appreciate that any term or terms with which these examples or illustrations are utilized encompass other embodiments as well as implementations and adaptations thereof which may or may not be given therewith or elsewhere in the specification and all such embodiments are intended to be included within the scope of that term or terms. Language designating such non-limiting examples and illustrations includes, but is not limited to: “for example,” “for instance,” “e.g.,” “in one embodiment,” and the like.

FIG. 1 depicts one embodiment of a topology which may be used to implement embodiments of the systems and methods disclosed herein. Topology 100 comprises a set of entities including vehicle data system 120 (also referred to herein as the TrueCar system) which is coupled through network 170 to computing devices 110 (e.g., computer systems, personal data assistants, kiosks, dedicated terminals, mobile telephones, smart phones, etc.), and one or more computing devices at inventory companies 140, original equipment manufacturers (OEM) 150, sales data companies 160, financial institutions 182, external information sources 184, departments of motor vehicles (DMV) 180 and one or more associated point of sale locations, in this embodiment, car dealers 130. Network 170 may be for example, a wireless or wireline communication network such as the Internet or wide area network (WAN), publicly switched telephone network (PTSN) or any other type of electronic or non-electronic communication link such as mail, courier services or the like.

Vehicle data system 120 may comprise one or more computer systems with central processing units executing instructions embodied on one or more computer readable media where the instructions are configured to perform at least some of the functionality associated with embodiments disclosed herein. These applications may include a vehicle data application 190 comprising one or more applications (instructions embodied on one or more non-transitory computer readable media) configured to implement an interface module 192, data gathering module 194 and processing module 196 utilized by the vehicle data system 120. Furthermore, vehicle data system 120 may include data store 122 operable to store obtained data 124, data 126 determined during operation, models 128 which may comprise a set of dealer cost model or price ratio models, or any other type of data associated with embodiments disclosed herein or determined during the implementation of those embodiments.

Vehicle data system 120 may provide a wide degree of functionality including utilizing one or more interfaces 192 configured to for example, receive and respond to queries from users at computing devices 110; interface with inventory companies 140, manufacturers 150, sales data companies 160, financial institutions 170, DMVs 180 or dealers 130 to obtain data; or provide data obtained, or determined, by vehicle data system 120 to any of inventory companies 140, manufacturers 150, sales data companies 160, financial institutions 182, DMVs 180, external data sources 184 or dealers 130. It will be understood that the particular interface 192 utilized in a given context may depend on the functionality being implemented by vehicle data system 120, the type of network 170 utilized to communicate with any particular entity, the type of data to be obtained or presented, the time interval at which data is obtained from the entities, the types of systems utilized at the various entities, etc. Thus, these interfaces may include, for example web pages, web services, a data entry or database application to which data can be entered or otherwise accessed by an operator, or almost any other type of interface which it is desired to utilize in a particular context.

In general, then, using these interfaces 192 vehicle data system 120 may obtain data from a variety of sources, including one or more of inventory companies 140, manufacturers 150, sales data companies 160, financial institutions 182, DMVs 180, external data sources 184 or dealers 130 and store such data in data store 122. This data may be then grouped, analyzed or otherwise processed by vehicle data system 120 to determine desired data 126 or models 128 which are also stored in data store 122. A user at computing device 110 may access the vehicle data system 120 through the provided interfaces 192 and specify certain parameters, such as a desired vehicle configuration or incentive data the user wishes to apply, if any. The vehicle data system 120 can select a particular set of data in the data store 122 based on the user specified parameters, process the set of data using processing module 196 and models 128, generate interfaces using interface module 192 using the selected data set and data determined from the processing, and present these interfaces to the user at the user's computing device 110. More specifically, in one embodiment interfaces 192 may visually present the selected data set to the user in a highly intuitive and useful manner.

In particular, in one embodiment, a visual interface may present at least a portion of the selected data set as a price curve, bar chart, histogram, etc. that reflects quantifiable prices or price ranges (e.g., “average,” “good,” “great,” “overpriced,” etc.) relative to reference pricing data points (e.g., invoice price, MSRP, dealer cost, market average, internet average, etc.). Using these types of visual presentations may enable a user to better understand the pricing data related to a specific vehicle configuration. Additionally, by presenting data corresponding to different vehicle configurations in a substantially identical manner, a user can easily make comparisons between pricing data associated with different vehicle configurations. To further aid the user's understanding of the presented data, the interface may also present data related to incentives which were utilized to determine the presented data or how such incentives were applied to determine presented data.

Turning to the various other entities in topology 100, dealer 130 may be a retail outlet for vehicles manufactured by one or more of OEMs 150. To track or otherwise manage sales, finance, parts, service, inventory and back office administration needs dealers 130 may employ a dealer management system (DMS) 132. Since many DMS 132 are Active Server Pages (ASP) based, transaction data 134 may be obtained directly from the DMS 132 with a “key” (for example, an ID and Password with set permissions within the DMS system 132) that enables data to be retrieved from the DMS system 132. Many dealers 130 may also have one or more web sites which may be accessed over network 170, where pricing data pertinent to the dealer 130 may be presented on those web sites, including any pre-determined, or upfront, pricing. This price is typically the “no haggle” price (i.e., price with no negotiation) and may be deemed a “fair” price by vehicle data system 120.

Inventory companies 140 may be one or more inventory polling companies, inventory management companies or listing aggregators which may obtain and store inventory data from one or more of dealers 130 (for example, obtaining such data from DMS 132). Inventory polling companies are typically commissioned by the dealer to pull data from a DMS 132 and format the data for use on websites and by other systems. Inventory management companies manually upload inventory information (photos, description, specifications) on behalf of the dealer. Listing aggregators get their data by “scraping” or “spidering” websites that display inventory content and receiving direct feeds from listing websites (for example, AutoTrader.com, FordVehicles.com, etc.).

DMVs 180 may collectively include any type of government entity to which a user provides data related to a vehicle. For example, when a user purchases a vehicle it must be registered with the state (for example, DMV, Secretary of State, etc.) for tax and titling purposes. This data typically includes vehicle attributes (for example, model year, make, model, mileage, etc.) and sales transaction prices for tax purposes.

Financial institution 182 may be any entity such as a bank, savings and loan, credit union, etc.

that provides any type of financial services to a participant involved in the purchase of a vehicle. For example, when a buyer purchases a vehicle they may utilize a loan from a financial institution, where the loan process usually requires two steps: applying for the loan and contracting the loan. These two steps may utilize vehicle and consumer information in order for the financial institution to properly assess and understand the risk profile of the loan. Typically, both the loan application and loan agreement include proposed and actual sales prices of the vehicle.

Sales data companies 160 may include any entities that collect any type of vehicle sales data.

For example, syndicated sales data companies aggregate new and used sales transaction data from the DMS 132 systems of particular dealers 130. These companies may have formal agreements with dealers 130 that enable them to retrieve data from the dealer 130 in order to syndicate the collected data for the purposes of internal analysis or external purchase of the data by other data companies, dealers, and OEMs.

Manufacturers 150 are those entities which actually build the vehicles sold by dealers 130. In order to guide the pricing of their vehicles, the manufacturers 150 may provide an Invoice price and a Manufacturer's Suggested Retail Price (MSRP) for both vehicles and options for those vehicles—to be used as general guidelines for the dealer's cost and price. These fixed prices are set by the manufacturer and may vary slightly by geographic region.

External information sources 184 may comprise any number of other various source, online or otherwise, which may provide other types of desired data, for example data regarding vehicles, pricing, demographics, economic conditions, markets, locale(s), consumers, etc.

It should be noted here that not all of the various entities depicted in topology 100 are necessary, or even desired, in embodiments disclosed herein, and that certain of the functionality described with respect to the entities depicted in topology 100 may be combined into a single entity or eliminated altogether. Additionally, in some embodiments other data sources not shown in topology 100 may be utilized. Topology 100 is therefore exemplary only and should in no way be taken as imposing any limitations on embodiments disclosed herein.

FIG. 2 depicts one embodiment of a model that transforms data into vehicle prices. In this example, the model may aggregate data from numerous sources and may transform the data into geo-specific vehicle prices on the TrueCar system.

FIG. 3 depicts one embodiment of data used to obtain vehicle price. In this example, various types of data may be supplied by and/or obtained from various sources for calculation of geo-specific vehicle prices. In one embodiment, a plurality of types of data collected may include transaction data, configurator data 300, offset data 305, census data 315, customer and dealer incentives 325, and industry data 335. In one embodiment, transaction data may contain details for new vehicle transactions including sales date, year, make, model, vehicle trim, transaction MSRP, transaction invoice, reported price, reported cost, days to turn, and customer and dealer ZIP Code.

In one embodiment, configurator data 300 may contain general features of vehicles by trim. Example features may include body type, base MSRP, base invoice, engine displacement and number of cylinders, fuel type, and number of doors.

In one embodiment, offset data 315 may include prices of vehicles offered by dealerships reported as an offset from MSRP. These may be referred to as dealer offsets.

In one embodiment, customer and dealer incentives data 325 may include dealer and customer cash incentives by date, location, and vehicle trim. In one embodiment, if an incentive is presently active for the vehicle trim and location specified by the user, the price may be adjusted accordingly.

In one embodiment, industry data 335 may include auto industry data by make and model. Example auto industry data may include sales, incentives dollars spent, inventory, and days supply of vehicle.

The various types of data collected at a TrueCar system can be appended to vehicle transactions in various ways. For example, as shown in FIG. 3, configurator data 300 and offset data 305 may be appended using trim_id; census data 315 may be appended using zip code; customer and dealer incentives data 325 may be appended using date, trim_id, and zip code; and industry data 335 may be appended using date and make/model. Vehicle transactions 345 may be used in data analysis 350 to produce a TrueCar average price for a vehicle.

Vehicle transaction activity varies widely across the United States and may be a function of population, consumer-based vehicle demand, and the density of dealers. In a geographic area of fixed size, such as ten square miles, one may find a large number of vehicle transactions in densely-populated urban regions and little or no transactions in sparsely populated rural areas. Additionally, the demand for certain vehicle characteristics may also vary widely. This may include market shares for vehicles produced in foreign countries tend to be smaller in what is known as the Rust Belt in the U.S.

In non-geo specific embodiments, vehicle price estimates could be made according to standard administrative and political boundaries. Examples of administrative and political boundaries may include U.S. states and U.S. Census regions. In embodiments disclosed herein, vehicle price estimates could be made at the Designated Market Areas (DMAs) level and, where possible, over smaller geographic areas. More specifically, embodiments disclosed herein utilize geographic demarcation points that can be more heavily based on the factors that influence car-buying behavior. DMAs, which are non-overlapping consumer-based geographic clusters, coupled with the postal ZIP Codes at which a TrueCar demand is measured, may allow construction of a simple, hierarchical geographical structure that covers every square inch of US land mass. In some embodiments, the hierarchical geographical structure may be described in the following steps:

(1) DMA to ZIP Code: A mapping of ZIP Codes to DMAs was acquired from the Nielson Media Research, the institution which built the DMAs. As of 2010, the mapping did not include every one of the known 42,333 ZIP Codes and therefore did not fully cover the land mass of the United States on which vehicle consumers may reside. To remedy this situation, in one embodiment, unmatched ZIP Codes are assigned to the DMAs. The assignment may be done by comparing the unmatched ZIP Code to all matched ZIP Codes with the same leading three digits. For example, to map ZIP Code 90401 to a DMA, it was compared with all ZIP Codes beginning with “904” and assigned to the same DMA as the ZIP Code with the 3-digit match and where the distance between the geographic centers of the matched ZIP Code and unmatched ZIP Code was the smallest.

(2) ZIP Code to ZIP Code Tabulation Area (ZCTA): In one embodiment, the smallest geographic unit for which data may be collected may be the postal ZIP Code. While every potential or actual vehicle buyer who has an address in the U.S. also has a distinct ZIP Code, the ZIP Codes do not necessarily have explicit geographic boundaries since they are based on postal routes and not distinct polygons. The U.S. Census Bureau created ZIP Code Tabulation Areas (ZCTAs) that partition the U.S. into a set of polygons that are non-overlapping and contain the entire land mass of the US. In one embodiment, all ZIP Codes are mapped into their appropriate ZCTAs based on a determination of whether the geographic center of each ZIP Code lies within the ZCTA polygon. In one embodiment, by determining if the centroid of a ZIP code was within the ZCTA polygon, it can be feasible to assign every ZIP Code to a ZCTA and, more importantly, to be able to use the explicit spatial relationships to determine if any two ZCTAs share a boundary.

(3) DMA to subDMA: In one embodiment, DMAs can be divided into non-overlapping polygons to create smaller regions whose construction favors consumer buying behavior over administrative boundaries. To divide DMAs into smaller areas—the resulting areas may be called “subDMAs”—the following steps are taken:

Step 1: Any ZCTA for which there were at least a number of vehicle transactions (say, 20) in a data set for a defined time period (say, a 16-week period ending on Jul. 31, 2010) can become a subDMA of the DMA to which it belongs.

Step 2: If there are not identifiable subDMAs based on the vehicle transaction rule, the DMA may not be divided and so may contain only one subDMA which is identical to the DMA.

Step 3: For every pair of ZCTAs, i and j, whose geographic centers are within a distance (say, 100 miles) of each other, a 6-dimensional spatial-socioeconomic difference may be computed in the following equation:

D _(i,j)=[GCD_(i,j) ²+Σ_(p=1) ⁵ |x _(i,p) −x _(j,p)|²]^(1/2)

where GCD_(i,j) can be the Great Circle Distance between the centroids of ZCTAs i and j and each of the p=1, . . . ,5 indexes may represent a rescaled (over [0,1]) feature of the ZCTA. All features that have been transformed to a numeric format can then be represented on scale bounded over [0,1] as follows:

$x_{i,p} = \frac{\left( {x_{i,p} - {\min\limits_{i}x_{.{,p}}}} \right)}{\left( {{\max\limits_{i}x_{.{,p}}} - {\min\limits_{i}x_{.{,p}}}} \right)}$

In one example embodiment, p may represent the following features in the following table:

p Feature 1 Labor force participation rate in the ZCTA based on the 2000 Census relative to national median 2 Percentage of households in a ZCTA living in a block categorized as “urban” during the 2000 Census relative to the national percentage 3 Average household income in the ZCTA based on the 2000 Census relative to the national income 4 Median asking price of homes in the ZCTA based on the 2000 Census relative to the national median asking price 5 Mean value of homes in the ZCTA relative to the national value

Step 4: For any ZCTA not designated as a subDMA based on vehicle transactions, that ZCTA can be merged with the subDMA for which it is both adjacent in a spatial sense and has the smallest value of d_(i,j) among its adjacencies. This can be a recursive process as explained in FIG. 4.

At step 400, a determination may be made whether there are at least two ZCTAs within the same DMA. If there are at least two ZCTAs within the same DMA, then at step 405, a determination may be made if at least one ZCTA meet the criteria for being a subDMA. If there are not at least two ZCTAs within the same DMA, then at step 410, there may not be merging of DMAs. If there is at least one ZCTA that meets the criteria for being a subDMA, then at step 415 a determination may be made if there is a ZCTA not assigned to a subDMA. If there is not at least one ZCTA that meets the criteria for being a subDMA then at step 420 there may not be merging of ZCTAs. If there is a ZCTA not assigned to a subDMA, then at step 425 a determination may be made if the ZCTA not assigned to a subDMA is adjacent to a ZCTA with an assigned subDMA. If there is not a ZCTA not assigned to a subDMA, then at step 430 there may not be merging of ZCTAs. If there is a ZCTA not assigned to a subDMA that is adjacent to a ZCTA with an assigned subDMA, then there can be a merging of the ZCTA without an assigned subDMA to the ZCTA with an assigned subDMA so that they both include the assigned subDMA at step 435. If there is not a ZCTA not assigned to a subDMA that is adjacent to a ZCTA with an assigned subDMA, then at step 440 there may not be a merging of ZCTAs. This method of merging ZCTAs in FIG. 4 may be understood by an example shown in FIG. 5.

FIG. 5 depicts three ZCTAs as ZCTA “A”, ZCTA “B” and ZCTA “C”. Applying the method in FIG. 4 to the ZCTA regions in FIG. 5, “A”, “B”, and “C” may be ZCTAs in the same DMA as in step 400. Next, a determination can be made that “A” is a valid ZCTA and meets the criteria for being a subDMA as in step 405. Moving onto step 415, a determination may be made that “B” and “C” are ZCTAs not yet assigned to a subDMA. In making the determination at step 425, “B” may be seen as adjacent to both “A” and “C.” “C” is not adjacent to “A”. In this example, at first “B” may join “A” to so that the subDMA includes both “A” and “B” as in step 435. Once “B” merges with “A”, “C” can then join the subDMA since it is adjacent to one of the ZCTAs in the subDMA as in step 435.

In one embodiment, there may be a total of 1941 subDMAs and 191 DMAs located. FIG. 6 provides an example of how the Los Angeles, CA DMA can be divided into 153 subDMAs using the steps specified above in FIG. 4.

(4) DMA to DMAGroup: Using a similar approach to merging polygons as used in the clustering of ZCTAs into subDMAs, DMAGroups may be built by merging adjacent DMAs based on spatial adjacency and similarity of socioeconomic characteristics. One example distinction: DMAGroups may contain DMAs that are up to 250 miles from one another. The DMAGroup may act as a geographic entity similar to a US state, though they may be more uniformly sized and reflect vehicle-buying behavior rather than administrative boundaries. In one embodiment, after applying these rules, there may be 131 DMAGroups with some containing a single DMA.

(5) DMAGroup-DMARegion: Using a similar approach to merging polygons as used in the clustering of DMAs into DMAGroups, DMARegions may be built by merging adjacent DMAGroups based on spatial adjacency and similarity of socioeconomic characteristics with one exception: DMARegions may contain DMAGroups that are up to 500 miles from one another. The DMARegion may act as a geographic entity similar to a US Census region, though they may be more uniformly sized and reflect vehicle-buying behavior rather than administrative boundaries. In one embodiment, after applying these rules, there may be 12 DMARegion: Alaska, Hawaii, and 10 others that cover the land mass of the Continental US.

As an example, the consumer-based hierarchy described above may be in the order as shown in FIG. 7. In this example, hierarchy 700 utilizes ZIP Code 702 as the smallest region. ZCTA 704, subDMA 706, DMA 708, DMAGroup 710, DMARegion 712, and All US 714 are positioned upstream from ZIP Code 702. This hierarchy may also be seen as: ZIP Code→ZCTA→subDMA→DMA→DMAGroup→DMARegion→All US

Every vehicle legally registered in the United States has a unique Vehicle Identification Number (VIN) that contains, among other information, the following vehicle features:

Year

Make

Model

Body Type.

The combination of these vehicle features may be referred to as YMMB and may be denoted by the subscript q. Furthermore, the index for a distinct vehicle may be denoted by the index i, and if that vehicle has the YMMB combination denoted by q, it may be stated as i ϵ q. Furthermore, for the vehicle make denoted by m, there may be an indication that an individual vehicle belongs to that make by stating that i ϵ m.

In one embodiment, to provide geo-specific price estimates, one could simply summarize all transactions for a specific vehicle in a particular geographic area. Two complications exist with this approach. First, the transactions data available to compute summary statistics may represent only about 40% of all vehicle transactions and so it may be regarded as a sample rather than the population of transactions. Second, for every possible combination of year, make, model, trim and option, the number of transactions available for each combination may be too small to draw inferences about vehicle prices.

In order to provide high-quality pricing estimates for a wide array of vehicles and areas, a flexible definition of “geo-specific” may be both geographic and data driven. At its finest resolution, vehicle transaction data may be collected at the ZIP Code level. At increasingly coarse levels of resolution, the spatial hierarchy detailed earlier can be: ZIP Code→ZCTA→subDMA→DMA→DMAGroup→DMARegion→All→US.

An estimation of pricing at the highest level of resolution may be possible provided that a quality standard is met. FIG. 8 provides an example of price estimation. In one embodiment, since the standard error of the estimated price may be inversely proportional to the sample size, std.err_(q)=σ_(q)/√{square root over (n_(q))}, where n_(q) may be the number of observations in bin q.

At step 800, there may be a determination of the geographic resolution at which the minimum threshold, n_(q)≥20, may be met for every YMMB bin, q. At step 805, for bin q, if the minimum threshold is met at the ZIP Code level, then the geo-specific price estimate may be computed for the ZIP Code at step 810. If the number of observations is less than 20 at step 815, then at step 820 a determination may be made if number of observations is less than 20 at the national level. If the number of observations is less than 20 at the national level, then the price is not estimated using this model at step 825. If the number of observations less than 20 is not at the national level, then the number of observations at the next level up is computed at step 830. This hierarchical evaluation continues until the minimum threshold n_(q) is met. If the threshold is not met at the highest level, the national level, then the price is not estimated using this model.

Geo-Specific Price Modeling After classifying transactions data into bins of vehicles having similar characteristics (e.g., the YMMB bins), a statistical pricing model for the vehicle pricing using the following operations may be utilized:

-   (a) Use of temporally-weighted historical data to generate a     sufficient number of observations needed to draw inferences with     acceptable confidence at the geo-specific level. -   (b) Use of geo-specific socioeconomic variables to account for     geographic differences in consumer behavior. Example geo-specific     socioeconomic variables may include median income and median home     prices. -   (c) Accounting for the effect of supply and demand of a vehicle     price. For example, sales velocity and days supply of vehicles. -   (d) Vehicle-specific attributes. Examples of vehicle-specific     attributes may include engine type and drive type. -   (e) Application of a mixed-effects regression model that is     spatially smoothed to reflect observed geographic biases.

1. Temporal Weighting of Historical Observations Every historical transaction, y_(i) can be used in the geo-specific modeling process. However, use of a transaction that occurred in the very distant past may cause misleading results, particularly if the new-car market has witnessed recent changes such as the presence of incentives, seasonal fluctuations, or programs like the 2010 “Cash-for-Clunkers” program. In one embodiment, to put emphasis on more recent transactions and thereby more quickly capture change, a temporal weight can be assigned to each observation based on its age:

w_(i)=e^(−ϕA) _(i) where A_(i) may be the age, in weeks, of observation y_(i) at the time when the pricing model is executed. FIG. 9 shows an example of weights with various degradation factors, ϕ. For any YMMB bin q, the number of observations weighted in a geo-specific region is

$n_{q} = {\sum\limits_{i \in q}w_{i}}$

and can be used to determine if a threshold (in this example, n_(q)≥20) is met for any bin/geo-specific combination.

It can be important to choose the appropriate value of degradation factor ϕ and also the minimum observation age for which historical observations are not used. FIG. 9 depicts a graph where line 900 represents the temporal weight function for factor ϕ set at 0.00; line 910 represents the temporal weight function for factor ϕ set at 0.01; line 920 represents the temporal weight function for factor ϕ set at 0.05; line 930 represents the temporal weight function for factor ϕ set at 0.10; and line 940 represents the temporal weight function for factor ϕ set at 0.20. As an example, various combinations of ϕ={0, 0.1, 0.2,3,4.5,0.6,0.7) and a week cutoff of 4, 8, 12, and 16 weeks were considered in an analysis of historical performance. Use of more than 4 weeks of data underperformed other combinations as a result of the persistence of dealer and customer incentive that had ended weeks earlier yet remained in the analysis. In this example, based on the analysis of historical performance, a value of ϕ=0.5 may be used and any observation older than 4 weeks at the time of analysis may not be used.

2. Geo-Specific Socioeconomic Data Because consumer demand may vary with geography based on the characteristics and taste of the local population, a set of variables z that includes geo-specific information obtained from our data providers and the US Census Bureau (based on their 2000 decennial census) may be used. This may include: 1) fraction of rural households in the locality compared to national percentage, 2) median home price in the locality compared to the national median home price, 3) percentage of work force participation in locality compared to national work force participation and, 4) the number of vehicle dealerships for a specific make in the locality.

3. Inventory Data As imbalance between consumer demand and dealer supply may affect prices, calendar and inventory in the geo-specific model may be accounted for and include a set of variables y that includes: 1) number of days the vehicle spent in lot before sale, 2) number of sales of a YMMB in the past four weeks (sales velocity), 3) a flag indicating that an individual transaction occurs at end of month, 4) industry-wide incentives offered for a particular make, model compared to overall incentives spent, and 5) days supply of a particular make and model.

4. Vehicle-Specific Data To account for structural and pricing differences in each vehicle, a set of variables x may be considered that include: 1) the natural logarithm of the MSRP of the base vehicle without options, 2) natural logarithm of the ratio of MSRP of the vehicle with options and the base vehicle, 3) the ratio of available customer cash for the vehicle in the sales region to the reported cost, 4) the ratio of available dealer cash for the vehicle in the sales region to the reported cost, 5) relative to cost, the difference between dealer cash available at the time of the transaction and the four-week average of the dealer cash, 5) relative to cost, the difference between customer cash available at the time of the transaction and the four-week average of the customer cash, 6) the vehicle body type such as SUV, Van or Truck), and 7) the number of cylinders in the vehicle's engine.

5. Mixed Effects Regression Model A mixed effects regression model may be built for the margin ratio (mr) defined as

${mr} = \frac{price}{\cos \; t}$

relative to its four-week mean value in the same bin q. The cost value may be based on a product of the transaction MSRP and a cost adjustment factor:

cost_(i)=transaction_(MSRPi)+cost adjustment factor_(q),

and the cost adjustment factor may be computed across all vehicles in the bin, q, and reflects the average ratio of vehicle cost relative to the transaction_MSRP, both inclusive of options.

The model can be summarized by a simple equation:

${\frac{price_{i}}{cost_{i}} - \left( \overset{\_}{\frac{price_{i}}{cost_{i}}} \right)_{q}} = {{{mr_{i}} - \overset{\_}{mr_{q}}} = {\alpha_{o} + \alpha_{m} + {\sum\limits_{j}{\beta_{j}x_{i}}} + {\sum\limits_{k}{\delta_{m}y_{i}}} + {\sum\limits_{l}{\lambda_{l}z_{i}}} + ɛ_{i}}}$ $\mspace{20mu} {\overset{\_}{mr_{q}} = \frac{\sum_{i \in q}{w_{i}mr_{i}}}{\sum_{i \in q}w_{i}}}$

In the preceding equation, the features in set x may represent a set of variables which impact the margin ratio such as vehicle attributes, the set y may represent industry data and vehicle supply and demand, and the set z may represent local-level customer and demographic information as well as industry-level data, α₀ can be a global intercept term, α_(m) can be a make-level intercept applied only when i ϵ m and

can denote a 4-week weighted average of the margin ratios for the particular YMMB bin q. The choice of the width of temporal window may vary over time if it is determined that a different window improves price prediction accuracy. To adjust for known geographic biases the error term, ϵ_(i) can be decomposed into two parts:

$ɛ_{i} = {{\rho {\sum\limits_{j \neq i}{{K\left( g_{i,j} \right)}ɛ_{j}}}} + e_{i}}$

where g_(i,j) may be the Great Circle Distance between an observation i and all observations j (computed based on the distance between the geocenters of their subDMAs), K may be a kernel such that

${K\left( g_{i,j} \right)} = \frac{1}{\sqrt{g_{i,j}}}$

if the observations are in different subDMAs and 0 otherwise, ϵ_(j) may be the error term from all other observations, and −1≤ρ≤1 may be the degree to which residuals are spatially correlated, and e_(i) may be the residual that exists after the estimated spatial autocorrelation has been removed.

The geo-specific price estimation model

${\frac{price_{i}}{cost_{i}} - \left( \overset{\_}{\frac{price_{i}}{cost_{i}}} \right)_{q}} = {{{mr_{i}} - \overset{\_}{mr_{q}}} = {\alpha_{o} + \alpha_{m} + {\sum\limits_{j}{\beta_{j}x_{i}}} + {\sum\limits_{k}{\delta_{m}y_{i}}} + {\sum\limits_{l}{\lambda_{l}z_{i}}} + {\rho {\sum\limits_{j \neq i}{{K\left( g_{i,j} \right)}ɛ_{j}}}} + e_{i}}}$

can then be estimated using weighed Ordinary Least Squares (OLS) to find the estimated parameters {circumflex over (α)}, {circumflex over (β)}, {circumflex over (δ)}, {circumflex over (λ)} and ρ that result in the smallest sum of temporally weighted squared residuals: Σ_(i)w_(i)e_(i) ². Given the results of the regression equation, the predicted margin ratio a vehicle in bin q can then be mr_(i)=mr_(i)+

he

mr_(i) may be th

edicated margin ratio that results from the model. The final estimated price for the vehicle in transaction i may then be price_(i)=mr_(i)×cost_(i).

To estimate the price for any vehicle in bin q within the local area, the following may be used to display price (on a website) for the base vehicle (i.e., without options) as:

=

×cost_(q).

Although this disclosure has been described with respect to specific embodiments, these embodiments are merely illustrative, and not restrictive of the invention disclosed herein. The description herein of illustrated embodiments of the invention, including the description in the Abstract and Summary, is not intended to be exhaustive or to limit the invention to the precise forms disclosed herein (and in particular, the inclusion of any particular embodiment, feature or function within the Abstract or Summary is not intended to limit the scope of the invention to such embodiment, feature or function). Rather, the description is intended to describe illustrative embodiments, features and functions in order to provide a person of ordinary skill in the art context to understand the invention without limiting the invention to any particularly described embodiment, feature or function, including any such embodiment feature or function described in the Abstract or Summary. While specific embodiments of, and examples for, the invention are described herein for illustrative purposes only, various equivalent modifications are possible within the spirit and scope of the invention, as those skilled in the relevant art will recognize and appreciate. As indicated, these modifications may be made to the invention in light of the foregoing description of illustrated embodiments of the invention and are to be included within the spirit and scope of the invention. Thus, while the invention has been described herein with reference to particular embodiments thereof, a latitude of modification, various changes and substitutions are intended in the foregoing disclosures, and it will be appreciated that in some instances some features of embodiments of the invention will be employed without a corresponding use of other features without departing from the scope and spirit of the invention as set forth. Therefore, many modifications may be made to adapt a particular situation or material to the essential scope and spirit of the invention.

Reference throughout this specification to “one embodiment”, “an embodiment”, or “a specific embodiment” or similar terminology means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment and may not necessarily be present in all embodiments. Thus, respective appearances of the phrases “in one embodiment”, “in an embodiment”, or “in a specific embodiment” or similar terminology in various places throughout this specification are not necessarily referring to the same embodiment. Furthermore, the particular features, structures, or characteristics of any particular embodiment may be combined in any suitable manner with one or more other embodiments. It is to be understood that other variations and modifications of the embodiments described and illustrated herein are possible in light of the teachings herein and are to be considered as part of the spirit and scope of the invention.

In the description herein, numerous specific details are provided, such as examples of components and/or methods, to provide a thorough understanding of embodiments of the invention. One skilled in the relevant art will recognize, however, that an embodiment may be able to be practiced without one or more of the specific details, or with other apparatus, systems, assemblies, methods, components, materials, parts, and/or the like. In other instances, well-known structures, components, systems, materials, or operations are not specifically shown or described in detail to avoid obscuring aspects of embodiments of the invention. While the invention may be illustrated by using a particular embodiment, this is not and does not limit the invention to any particular embodiment and a person of ordinary skill in the art will recognize that additional embodiments are readily understandable and are a part of this invention.

Any suitable programming language can be used to implement the routines, methods or programs of embodiments of the invention described herein, including C, C++, Java, assembly language, etc. Different programming techniques can be employed such as procedural or object oriented. Any particular routine can execute on a single computer processing device or multiple computer processing devices, a single computer processor or multiple computer processors. Data may be stored in a single storage medium or distributed through multiple storage mediums, and may reside in a single database or multiple databases (or other data storage techniques). Although the steps, operations, or computations may be presented in a specific order, this order may be changed in different embodiments. In some embodiments, to the extent multiple steps are shown as sequential in this specification, some combination of such steps in alternative embodiments may be performed at the same time. The sequence of operations described herein can be interrupted, suspended, or otherwise controlled by another process, such as an operating system, kernel, etc. The routines can operate in an operating system environment or as stand-alone routines. Functions, routines, methods, steps and operations described herein can be performed in hardware, software, firmware or any combination thereof.

Embodiments described herein can be implemented in the form of control logic in software or hardware or a combination of both. The control logic may be stored in an information storage medium, such as a computer-readable medium, as a plurality of instructions adapted to direct an information processing device to perform a set of steps disclosed in the various embodiments. Based on the disclosure and teachings provided herein, a person of ordinary skill in the art will appreciate other ways and/or methods to implement the invention.

It is also within the spirit and scope of the invention to implement in software programming or code an of the steps, operations, methods, routines or portions thereof described herein, where such software programming or code can be stored in a computer-readable medium and can be operated on by a processor to permit a computer to perform any of the steps, operations, methods, routines or portions thereof described herein. The invention may be implemented by using software programming or code in one or more general purpose digital computers, by using application specific integrated circuits, programmable logic devices, field programmable gate arrays, optical, chemical, biological, quantum or nanoengineered systems, components and mechanisms may be used. In general, the functions of the invention can be achieved by any means as is known in the art. For example, distributed or networked systems, components and circuits can be used. In another example, communication or transfer (or otherwise moving from one place to another) of data may be wired, wireless, or by any other means.

A “computer-readable medium” may be any medium that can contain, store, communicate, propagate, or transport the program for use by or in connection with the instruction execution system, apparatus, system or device. The computer readable medium can be, by way of example only but not by limitation, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, system, device, propagation medium, or computer memory. Such computer-readable medium shall generally be machine readable and include software programming or code that can be human readable (e.g., source code) or machine readable (e.g., object code).

A “processor” includes any, hardware system, mechanism or component that processes data, signals or other information. A processor can include a system with a general-purpose central processing unit, multiple processing units, dedicated circuitry for achieving functionality, or other systems. Processing need not be limited to a geographic location, or have temporal limitations. For example, a processor can perform its functions in “real-time,” “offline,” in a “batch mode,” etc. Portions of processing can be performed at different times and at different locations, by different (or the same) processing systems.

It will also be appreciated that one or more of the elements depicted in the drawings/figures can also be implemented in a more separated or integrated manner, or even removed or rendered as inoperable in certain cases, as is useful in accordance with a particular application. Additionally, any signal arrows in the drawings/Figures should be considered only as exemplary, and not limiting, unless otherwise specifically noted.

Furthermore, the term “or” as used herein is generally intended to mean “and/or” unless otherwise indicated. As used herein, including the claims that follow, a term preceded by “a” or “an” (and “the” when antecedent basis is “a” or “an”) includes both singular and plural of such term, unless clearly indicated within the claim otherwise (i.e., that the reference “a” or “an” clearly indicates only the singular or only the plural). Also, as used in the description herein and throughout the claims that follow, the meaning of “in” includes “in” and “on” unless the context clearly dictates otherwise. The scope of the present disclosure should be determined by the following claims and their legal equivalents. 

What is claimed is:
 1. A vehicle data system comprising: a processor; a non-transitory computer readable medium comprising computer code for processing distributed vehicle data, the computer code comprising code for: obtaining a set of historical transaction records from a first set of distributed sources; enhancing the historical transaction records with additional vehicle data collected from a second set of distributed sources; binning the historical transaction records based on at least one vehicle attribute and geographical hierarchy; providing a web page to a client computer, the web page having one or more input fields for a user to provide a user-specified vehicle configuration comprising a set of user-specified vehicle attributes; receiving over a network via the web page the user-specified vehicle configuration; generating a responsive web page in response to the user submitting the user-specified vehicle configuration, comprising: applying a set of rules to select a bin of enhanced historical transaction records as a function of a user geography and the user specified vehicle configuration; determining a margin ratio for the user specified vehicle configuration by: applying a set of temporal weighting rules to the enhanced historical transaction records of the selected bin; applying a set of geography specific socioeconomic rules to the enhanced historical transaction records of the selected bin, the geography specific rules selected based on the user geography; applying a set of vehicle rules to the enhanced historical transaction records of the selected bin, the set of vehicle rules selected based on the user specified vehicle configuration; determining an estimated price corresponding to the user specified vehicle attributes based on the determined margin ratio; generating HTML to cause a browser at the client computer to display the estimated price; sending the HTML to the client computer.
 2. The vehicle data system of claim 1, wherein enhancing the set of historical transaction records comprises: obtaining configurator data, offset data or census data from the second set of distributed sources; correlating the configurator data, offset data or census data with a historical transaction record using a trim identifier or geographic identifier; and enhancing the historical transaction record by storing the configurator data, offset data or census data in the correlated historical transaction record.
 3. The vehicle data system of claim 1, wherein the first set of rules for selecting the bin of historical transaction data are based on the geographical hierarchy.
 4. The vehicle data system of claim 3, wherein the first set of rules selects the bin of historical transaction data at a lowest level in the geographical hierarchy where a threshold number of historical transaction records exists.
 5. The vehicle data system of claim 4, wherein the geographical hierarchy includes a set of ordered geographical regions, including ZIP Code, ZIP Code Tabulation Area (ZCTA), subDMA, Designated Market Area (DMA), DMAGroup, DMARegion and the entire United States.
 6. The vehicle data system of claim 5, wherein the geographical regions of the geographical hierarchy are determined by applying a set of geographical hierarchy rules to the set of geographical regions.
 7. The vehicle data system of claim 6, where the geographical hierarchy rules comprise a set of ZIP Code to DMA rules, a set of ZIP Code to ZCTA rules, a set of DMA to subDMA rules, a set of DMA to DMAGroup rules, and a set of DMAGroup to DMARegion rules.
 8. The vehicle data system of claim 7, wherein the set of DMA to subDMA rules comprise: assigning any ZCTA for which there are at least a threshold number of associated historical transactions as a subDMA of the DMA to which it belongs; for each DMA which has no identifiable subDMAs, assigning a subDMA to that DMA, wherein the subDMA is equivalent to that DMA; and for any ZCTA not designated as a subDMA based on the threshold number of vehicle transactions, merging that ZCTA with a geographically closest DMA that has a smallest value for a socioeconomic difference indicator.
 9. A vehicle data system comprising: a processor; a non-transitory computer readable medium comprising computer code for processing distributed vehicle data, the computer code comprising code for: obtaining a set of historical transaction records from a first set of distributed sources, each transaction record; binning the historical transaction records based on at least one vehicle attribute and geographical hierarchy; providing a web page to a client computer, the web page having one or more input fields for a user to provide a user-specified vehicle configuration comprising a set of user-specified vehicle attributes; receiving over a network via the web page the page the user-specified vehicle configuration; generating a responsive web page in response to the user submitting the user-specified vehicle configuration, generating the responsive web page comprising: applying a set of rules to select a bin of historical transaction records as a function of a user geography and the user specified vehicle configuration; determining a margin ratio for the user specified vehicle configuration by:’ applying a set of temporal weighting rules to the historical transaction records of the selected bin; applying a set of geography specific socioeconomic rules to the historical transaction records of the selected bin, the geography specific rules selected based on the user geography; applying a set of vehicle rules to the historical transaction records of the selected bin, the set of vehicle rules selected based on the user specified vehicle configuration; determining an estimated price corresponding to the user specified vehicle attributes based on the determined margin ratio; generating HTML to cause a browser at the client computer to display the estimated price; communicating the responsive web page to the client computer.
 10. The vehicle data system of claim 9, comprising code for enhancing the historical transaction records with additional vehicle data collected from a second set of distributed sources.
 11. The vehicle data system of claim 10, wherein enhancing the set of historical transaction records comprises: obtaining configurator data, offset data or census data from the second set of distributed sources; correlating the configurator data, offset data or census data with a historical transaction record using a trim identifier or geographic identifier; and enhancing the historical transaction record by storing the configurator data, offset data or census data in the correlated historical transaction record.
 12. The vehicle data system of claim 9, wherein the first set of rules for selecting the bin of historical transaction data are based on the geographical hierarchy.
 13. The vehicle data system of claim 12, wherein the first set of rules selects the bin of historical transaction data at a lowest level in the geographical hierarchy where a threshold number of historical transaction records exists.
 14. The vehicle data system of claim 13, wherein the geographical hierarchy includes a set of ordered geographical regions, including ZIP Code, ZIP Code Tabulation Area (ZCTA), subDMA, Designated Market Area (DMA), DMAGroup, DMARegion and the entire United States.
 15. The vehicle data system of claim 14, wherein the geographical regions of the geographical hierarchy are determined by applying a set of geographical hierarchy rules to the set of geographical regions.
 16. The vehicle data system of claim 15, where the geographical hierarchy rules comprise a set of ZIP Code to DMA rules, a set of ZIP Code to ZCTA rules, a set of DMA to subDMA rules, a set of DMA to DMAGroup rules, and a set of DMAGroup to DMARegion rules.
 17. The vehicle data system of claim 16, wherein the set of DMA to subDMA rules comprise: assigning any ZCTA for which there are at least a threshold number of associated historical transactions as a subDMA of the DMA to which it belongs; for each DMA which has no identifiable subDMAs, assigning a subDMA to that DMA, wherein the subDMA is equivalent to that DMA; and for any ZCTA not designated as a subDMA based on the threshold number of vehicle transactions, merging that ZCTA with a geographically closest DMA that has a smallest value for a socioeconomic difference indicator.
 18. A vehicle data system comprising: a processor; a non-transitory computer readable medium comprising computer code for processing distributed vehicle data, the computer code comprising code for: obtaining a set of historical transaction records from a first set of distributed sources, each transaction record associated with a corresponding vehicle identification number (VIN); enhancing the historical transaction records with additional vehicle data collected from a second set of distributed sources by VIN; generating a dealer cost model for each of a set of manufacturers based on invoice data corresponding to that manufacturer, each dealer cost model defining holdback as a function of one or more additional pieces of invoice data; binning the historical transaction records based on at least one vehicle attribute and geography hierarchy; generating a price ratio model for each bin based on multivariable regression analysis of a set of vehicle attributes in the enhanced historical transaction records corresponding to that bin, each price ratio model defining price ratio as a function of one or more vehicle attributes in the set of vehicle attributes; providing a web page to a client computer, the web page having one or more input fields for a user to provide a user-specified vehicle configuration comprising a set of user-specified vehicle attributes; receiving over a network via the web page the user-specified vehicle configuration; generating a responsive web page in response to the user submitting the user-specified vehicle configuration comprising: applying a first set of rules to select a bin based on the set of user-specified vehicle attributes, the first set of rules selected based on at least one user-specified vehicle attribute and geography; applying a second set of rules to select a dealer cost model based on at least one user-specified vehicle attribute; applying the selected dealer cost model to a set of enhanced historical transaction records corresponding to the selected bin to generate a dealer cost; applying the selected price ratio model corresponding to the selected bin to the set of enhanced historical transaction records corresponding to the selected bin to generate a price ratio; generating an average price paid for the user-specified vehicle configuration as a function of dealer cost and price ratio; generating one or more relative price ranges based on the average price paid for the user-specified vehicle configuration and a standard deviation of historical pricing data determined from the set of enhanced historical transaction records corresponding to the selected bin; fitting a curve fit to the price data from the set of enhanced historical transaction records corresponding to the selected bin; determining a margin ratio for the user specified vehicle configuration by: applying a set of temporal weighting rules to the set of enhanced historical transaction records of the selected bin; applying a set of geography specific socioeconomic rules to the enhanced historical transaction records of the selected bin, the geography specific rules selected based on the user geography; applying a set of vehicle rules to the enhanced historical transaction records of the selected bin, the set of vehicle rules selected based on the user specified vehicle configuration; determining an estimated price corresponding to the user specified vehicle attributes based on the determined margin ratio; generating HTML to cause a browser at the client computer to display the curve with the relative prices ranges visually represented on the curve and the estimated price; sending the HTML to the client computer. 